After a GW client update a broken pattern scan resolves to null and the
feature dies quietly with no log. This makes such failures visible:

- GWCA.cpp: a [SCAN-HEALTH] summary after module init that re-emits every
  NULL scan / FAILED hook from the central registry into Py4GW_injection_log.txt.
- +31 Logger::AssertAddress calls closing coverage gaps across managers
  (MemoryMgr had 0; also UIMgr, ItemMgr, MapMgr, AgentMgr, ChatMgr, StoCMgr).
- SkillbarMgr: assert the TemplatesHelpers scans unconditionally (outside the
  if-guard) so a broken scan is logged instead of staying silently null.
- UIMgr: fix DestroyUIComponent FrApi.cpp assertion path (\Code\Engine\Frame),
  a pre-existing silent-null scan surfaced by the new logging.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>